Skip to main content

Chapter 3: Invoice Creation and Posting System

Now that you've learned how the Service Charge Calculation Engine computes all your monthly service charges, it's time to turn those calculations into real invoices that you can send to tenants. Welcome to the Invoice Creation and Posting System - your digital billing department!

What Problem Does This Solve?​

Imagine you've just calculated service charges for 100 rental units using the calculation engine. You now have all the amounts, but they're just numbers on a screen. You need to:

  • Transform calculations into formal invoices with proper document numbers
  • Post them to the financial system so they appear in tenant accounts
  • Handle large volumes efficiently without freezing your computer
  • Track what worked and what failed for audit purposes

Instead of manually creating each invoice (which would take days), the Invoice Creation and Posting System acts like a high-speed billing department that automatically processes hundreds of invoices in the background while you work on other tasks.

A Real-World Example​

Let's say you have 50 apartments with calculated February service charges totaling $25,000. Here's what the system will do:

Input: 50 calculated service charge records Processing: Creates 50 individual invoices in background jobs Output: 50 formal invoice documents posted to SAP Financial system Result: Tenants can now see their February service charges in their accounts

Key Components of the Invoice System​

The system consists of four main parts:

1. Data Selection and Display​

This shows you all the calculated charges ready for invoicing:

METHOD get_service_charges_data.
  SELECT * FROM zpost_serv_chrg
    INTO TABLE @DATA(lt_results)
    WHERE status = 'S'
      AND bukrs IN @s_bukrs.
ENDMETHOD.

This code finds all successfully calculated service charges that are ready to be turned into invoices. Think of this as gathering all your completed calculation worksheets from your desk.

2. Selection Interface​

This lets you choose which charges to process:

PARAMETERS: p_test RADIOBUTTON GROUP r1 DEFAULT 'X',
            p_upd  RADIOBUTTON GROUP r1.
SELECT-OPTIONS: s_bukrs FOR vicncn-bukrs,
                s_cont  FOR vicncn-recnnr.

You can choose test mode (to see what would happen) or update mode (to actually create invoices), and specify which company codes and contracts to process.

3. Background Job Creation​

This handles the heavy lifting of creating multiple invoices:

DEFINE open_job.
  lv_jobname = &1 && '_' && &2.
  CALL FUNCTION 'JOB_OPEN'
    EXPORTING jobname = lv_jobname
    IMPORTING jobcount = lv_jobcount.
END-OF-DEFINITION.

This code creates background jobs - like hiring temporary workers to process invoices while you do other work. Each job handles one contract at a time.

4. Status Tracking and Logging​

This monitors progress and captures results:

METHOD get_bal_logs.
  CALL FUNCTION 'BAL_DB_SEARCH'
    EXPORTING i_s_log_filter = ls_log_filter
    IMPORTING e_t_log_header = lt_log_header.
ENDMETHOD.

This retrieves processing logs to show you which invoices were created successfully and which had problems.

How to Use the Invoice System​

Here's how you would create invoices step by step:

Step 1: Access the Invoice Creation Screen​

From the Service Charge Dashboard, click the "Invoice Creation" button to launch the invoice processing program.

Step 2: Choose Your Processing Mode​

PARAMETERS: p_test RADIOBUTTON GROUP r1 DEFAULT 'X',
            p_upd  RADIOBUTTON GROUP r1.

Select Test Mode to see what would happen without actually creating invoices, or Update Mode to create real invoices.

Step 3: Select Your Data​

The system displays all calculated service charges in a table with checkboxes. You can:

  • Select All to process everything
  • Select individually for specific contracts
  • Review amounts before processing

Step 4: Execute Invoice Creation​

Click the "POST" button, and the system will:

  • Create background jobs for each selected contract
  • Process invoices in the background
  • Show you the results when complete

What Happens Under the Hood?​

Let's trace through what happens when you create invoices:

Here's what happens step by step:

Step 1: Data Preparation​

METHOD data_display.
  cl_salv_table=>factory(
    IMPORTING r_salv_table = go_alv
    CHANGING t_table = gt_results[] ).
ENDMETHOD.

The system displays calculated charges in an interactive table where you can select which ones to process. This is like reviewing a stack of invoices before sending them out.

Step 2: Job Creation​

LOOP AT gt_results WHERE sel IS NOT INITIAL.
  lv_jobname = lv_recnnr && '_' && sy-uname.
  open_job lv_recnnr sy-uname.
ENDLOOP.

For each selected contract, the system creates a separate background job. This is like assigning each invoice to a different clerk to process simultaneously.

Step 3: Invoice Processing​

SUBMIT rfrerapp_single 
  WITH p_bukrs   EQ lv_bukrs
  WITH p_recnnr  EQ lv_recnnr
  WITH p_month   EQ lv_month
  VIA JOB lv_jobname NUMBER lv_jobcount.

Each background job calls SAP's standard invoice program with the specific contract details. This is like each clerk using the official invoice creation process.

Step 4: Status Monitoring​

DO 1000 TIMES.
  CALL FUNCTION 'BP_JOB_STATUS_GET'
    EXPORTING jobname = ls_job-jobname
    IMPORTING status = lv_status.
  IF lv_status <> 'R'. EXIT. ENDIF.
ENDDO.

The system waits for all jobs to complete before proceeding. This is like waiting for all clerks to finish their work before collecting the results.

The System's Smart Features​

1. Test Mode Safety​

IF p_test IS NOT INITIAL.
  lv_pmode = 'S'.  " Simulate only
ELSEIF p_upd IS NOT INITIAL.  
  lv_pmode = 'E'.  " Execute for real
ENDIF.

Test mode lets you see exactly what will happen without creating real invoices. This prevents costly mistakes.

2. Batch Processing Efficiency​

LOOP AT gt_results WHERE sel IS NOT INITIAL.
  " Process each contract in separate background job
ENDLOOP.

The system processes multiple invoices simultaneously using background jobs, making it much faster than sequential processing.

3. Comprehensive Logging​

METHOD get_bal_logs.
  " Retrieves detailed logs for each processing attempt
  " Shows success/failure status with error messages
ENDMETHOD.

Every operation is logged with detailed status information, making it easy to troubleshoot problems and verify results.

4. Document Integration​

SELECT DISTINCT bukrs belnr gjahr vertn xblnr
  FROM bsid INTO TABLE lt_bsid
  WHERE xblnr = gt_bal_log-extnumber.

The system automatically finds created invoice documents in the financial system and displays them to you, proving that the invoices were actually created.

Real-World Processing Example​

Let's walk through a complete example:

Scenario: Create invoices for 3 apartments with calculated February charges

Step 1: Select test mode and the 3 contracts Step 2: Click "POST" button Step 3: System creates 3 background jobs simultaneously Step 4: Each job processes one contract:

  • Job 1: Creates invoice for Apartment A ($250)
  • Job 2: Creates invoice for Apartment B ($300)
  • Job 3: Creates invoice for Apartment C ($275)

Step 5: System waits for all jobs to complete Step 6: Collects results and shows success message Result: 3 formal invoices posted to tenant accounts totaling $825

Advanced Features​

Selective Processing​

lr_column->set_cell_type( if_salv_c_cell_type=>checkbox_hotspot ).

The system provides clickable checkboxes so you can select exactly which contracts to process, giving you fine-grained control.

Error Handling​

IF sy-subrc = 0.
  MESSAGE 'Invoices have been posted successfully' TYPE 'I'.
ELSE.
  " Handle errors appropriately
ENDIF.

The system checks for errors at each step and provides clear messages about what succeeded or failed.

Progress Tracking​

The system uses the Logging and Status Tracking System to provide detailed progress information and help you troubleshoot any issues.

Conclusion​

The Invoice Creation and Posting System serves as your automated billing department, transforming calculated service charges into formal invoices that integrate seamlessly with SAP's financial system. Like a well-organized billing office, it handles the complex process of document creation, posting, and tracking while keeping you informed of progress and results.

Key benefits:

  • Batch processing handles large volumes efficiently
  • Test mode prevents costly mistakes
  • Background jobs don't interfere with your other work
  • Comprehensive logging provides full audit trails
  • Automatic integration with SAP Financial modules

The system works closely with the Background Job Processing Framework to manage concurrent processing and relies on the Data Selection and Validation Engine to ensure data quality.

In our next chapter, we'll explore the Data Selection and Validation Engine to understand how the system ensures that only valid, complete data gets processed into invoices.